Heterogeneous Storage Arrays

ABSTRACT

A storage cluster is provided. The storage cluster includes a plurality of storage nodes coupled together as the storage cluster. The plurality of storage nodes is configured to assign data to two or more logical arrays and the plurality of storage nodes is configured to establish data striping across the plurality of storage nodes for user data of each of the two or more logical arrays.

BACKGROUND

Solid-state memory, such as flash, is currently in use in solid-statedrives (SSD) to augment or replace conventional hard disk drives (HDD),writable CD (compact disk) or writable DVD (digital versatile disk)drives, collectively known as spinning media, and tape drives, forstorage of large amounts of data. Flash and other solid-state memorieshave characteristics that differ from spinning media. Yet, manysolid-state drives are designed to conform to hard disk drive standardsfor compatibility reasons, which makes it difficult to provide enhancedfeatures or take advantage of unique aspects of flash and othersolid-state memory, such as the ability to partition arrays.

It is within this context that the embodiments arise.

SUMMARY

In some embodiments, a storage cluster is provided. The storage clusterincludes a plurality of storage nodes coupled together as the storagecluster. The plurality of storage nodes is configured to assign data totwo or more logical arrays and the plurality of storage nodes isconfigured to establish data striping across the plurality of storagenodes for user data of each of the two or more logical arrays.

In some embodiments, a storage cluster is provided. The storage clusterincludes a plurality of storage nodes coupled together as the storagecluster. The plurality of storage nodes is configured to assign data totwo or more logical arrays and the plurality of storage nodes isconfigured to establish data striping across the plurality of storagenodes for user data of each of the two or more logical arrays.

In some embodiments, a method for data striping across storage nodes ina storage cluster is provided. The method includes creating at least afirst logical array and a second logical array in a plurality of storagenodes of a storage cluster and performing data striping for first userdata, of which the first logical array has ownership, across theplurality of storage nodes. The method includes performing data stripingfor second user data, of which the second logical array has ownership,across the plurality of storage nodes.

Other aspects and advantages of the embodiments will become apparentfrom the following detailed description taken in conjunction with theaccompanying drawings which illustrate, by way of example, theprinciples of the described embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

The described embodiments and the advantages thereof may best beunderstood by reference to the following description taken inconjunction with the accompanying drawings. These drawings in no waylimit any changes in form and detail that may be made to the describedembodiments by one skilled in the art without departing from the spiritand scope of the described embodiments.

FIG. 1 is a perspective view of a storage cluster with multiple storagenodes and internal storage coupled to each storage node to providenetwork attached storage, in accordance with some embodiments.

FIG. 2 is a block diagram showing an interconnect switch couplingmultiple storage nodes in accordance with some embodiments.

FIG. 3 is a multiple level block diagram, showing contents of a storagenode and contents of one of the non-volatile solid state storage unitsin accordance with some embodiments.

FIG. 4 is a front view of a storage cluster, in a single chassis,partitioned into multiple logical arrays or clusters.

FIG. 5 is a front view of a storage cluster spanning two chassis,partitioned into multiple logical arrays or clusters.

FIG. 6 is a flow diagram of a method for partitioning a storage clusterinto multiple logical arrays and performing data striping of user datain accordance with the multiple logical arrays, which can be practicedon embodiments of the storage cluster, storage nodes and storage unitsof FIGS. 1-5.

FIG. 7 is an illustration showing an exemplary computing device whichmay implement the embodiments described herein.

DETAILED DESCRIPTION

A storage cluster, with storage nodes and storage units that havestorage memory, can be partitioned into two or more logical arrays. Insome embodiments, this occurs in a single chassis, and in someembodiments this can occur across multiple chassis. Each logical arrayacts as a storage cluster and can have software independent of anotherlogical array. Various degrees of sharing or isolation from one logicalarray to another are possible in various embodiments. Aspects of thestorage cluster, storage nodes and storage units are described hereinwith reference to FIGS. 1-3. Aspects of partitioning into multiplelogical arrays are described with reference to FIGS. 4-6.

The embodiments below describe a storage cluster that stores user data,such as user data originating from one or more user or client systems orother sources external to the storage cluster. The storage clusterdistributes user data across storage nodes housed within a chassis,using erasure coding and redundant copies of metadata. Erasure codingrefers to a method of data protection or reconstruction in which data isstored across a set of different locations, such as disks, storage nodesor geographic locations. Flash memory is one type of solid-state memorythat may be integrated with the embodiments, although the embodimentsmay be extended to other types of solid-state memory or other storagemedium, including non-solid state memory. Control of storage locationsand workloads are distributed across the storage locations in aclustered peer-to-peer system. Tasks such as mediating communicationsbetween the various storage nodes, detecting when a storage node hasbecome unavailable, and balancing I/Os (inputs and outputs) across thevarious storage nodes, are all handled on a distributed basis. Data islaid out or distributed across multiple storage nodes in data fragmentsor stripes that support data recovery in some embodiments. Ownership ofdata can be reassigned within a cluster, independent of input and outputpatterns. This architecture described in more detail below allows astorage node in the cluster to fail, with the system remainingoperational, since the data can be reconstructed from other storagenodes and thus remain available for input and output operations. Invarious embodiments, a storage node may be referred to as a clusternode, a blade, or a server.

The storage cluster is contained within a chassis, i.e., an enclosurehousing one or more storage nodes. A mechanism to provide power to eachstorage node, such as a power distribution bus, and a communicationmechanism, such as a communication bus that enables communicationbetween the storage nodes are included within the chassis. The storagecluster can run as an independent system in one location according tosome embodiments. In one embodiment, a chassis contains at least twoinstances of both the power distribution and the communication bus whichmay be enabled or disabled independently. The internal communication busmay be an Ethernet bus, however, other technologies such as PeripheralComponent Interconnect (PCI) Express, InfiniBand, and others, areequally suitable. The chassis provides a port for an externalcommunication bus for enabling communication between multiple chassis,directly or through a switch, and with client systems. The externalcommunication may use a technology such as Ethernet, InfiniBand, FibreChannel, etc. In some embodiments, the external communication bus usesdifferent communication bus technologies for inter-chassis and clientcommunication. If a switch is deployed within or between chassis, theswitch may act as a translation between multiple protocols ortechnologies. When multiple chassis are connected to define a storagecluster, the storage cluster may be accessed by a client using eitherproprietary interfaces or standard interfaces such as network filesystem (NFS), common internet file system (CIFS), small computer systeminterface (SCSI) or hypertext transfer protocol (HTTP). Translation fromthe client protocol may occur at the switch, chassis externalcommunication bus or within each storage node.

Each storage node may be one or more storage servers and each storageserver is connected to one or more non-volatile solid state memoryunits, which may be referred to as storage units. One embodimentincludes a single storage server in each storage node and between one toeight non-volatile solid state memory units, however this one example isnot meant to be limiting. The storage server may include a processor,dynamic random access memory (DRAM) and interfaces for the internalcommunication bus and power distribution for each of the power buses.Inside the storage node, the interfaces and storage unit share acommunication bus, e.g., PCI Express, in some embodiments. Thenon-volatile solid state memory units may directly access the internalcommunication bus interface through a storage node communication bus, orrequest the storage node to access the bus interface. The non-volatilesolid state memory unit contains an embedded central processing unit(CPU), solid state storage controller, and a quantity of solid statemass storage, e.g., between 2-32 terabytes (TB) in some embodiments. Anembedded volatile storage medium, such as DRAM, and an energy reserveapparatus are included in the non-volatile solid state memory unit. Insome embodiments, the energy reserve apparatus is a capacitor,super-capacitor, or battery that enables transferring a subset of DRAMcontents to a stable storage medium in the case of power loss. In someembodiments, the non-volatile solid state memory unit is constructedwith a storage class memory, such as phase change or magnetoresistiverandom access memory (MRAM) that substitutes for DRAM and enables areduced power hold-up apparatus.

One of many features of the storage nodes and non-volatile solid statestorage is the ability to proactively rebuild data in a storage cluster.The storage nodes and non-volatile solid state storage can determinewhen a storage node or non-volatile solid state storage in the storagecluster is unreachable, independent of whether there is an attempt toread data involving that storage node or non-volatile solid statestorage. The storage nodes and non-volatile solid state storage thencooperate to recover and rebuild the data in at least partially newlocations. This constitutes a proactive rebuild, in that the systemrebuilds data without waiting until the data is needed for a read accessinitiated from a client system employing the storage cluster. These andfurther details of the storage memory and operation thereof arediscussed below.

FIG. 1 is a perspective view of a storage cluster 160, with multiplestorage nodes 150 and internal solid-state memory coupled to eachstorage node to provide network attached storage or storage areanetwork, in accordance with some embodiments. A network attachedstorage, storage area network, or a storage cluster, or other storagememory, could include one or more storage clusters 160, each having oneor more storage nodes 150, in a flexible and reconfigurable arrangementof both the physical components and the amount of storage memoryprovided thereby. The storage cluster 160 is designed to fit in a rack,and one or more racks can be set up and populated as desired for thestorage memory. The storage cluster 160 has a chassis 138 havingmultiple slots 142. It should be appreciated that chassis 138 may bereferred to as a housing, enclosure, or rack unit. In one embodiment,the chassis 138 has fourteen slots 142, although other numbers of slotsare readily devised. For example, some embodiments have four slots,eight slots, sixteen slots, thirty-two slots, or other suitable numberof slots. Each slot 142 can accommodate one storage node 150 in someembodiments. Chassis 138 includes flaps 148 that can be utilized tomount the chassis 138 on a rack. Fans 144 provide air circulation forcooling of the storage nodes 150 and components thereof, although othercooling components could be used, or an embodiment could be devisedwithout cooling components. A switch fabric 146 couples storage nodes150 within chassis 138 together and to a network for communication tothe memory. In an embodiment depicted in FIG. 1, the slots 142 to theleft of the switch fabric 146 and fans 144 are shown occupied by storagenodes 150, while the slots 142 to the right of the switch fabric 146 andfans 144 are empty and available for insertion of storage node 150 forillustrative purposes. This configuration is one example, and one ormore storage nodes 150 could occupy the slots 142 in various furtherarrangements. The storage node arrangements need not be sequential oradjacent in some embodiments. Storage nodes 150 are hot pluggable,meaning that a storage node 150 can be inserted into a slot 142 in thechassis 138, or removed from a slot 142, without stopping or poweringdown the system. Upon insertion or removal of storage node 150 from slot142, the system automatically reconfigures in order to recognize andadapt to the change. Reconfiguration, in some embodiments, includesrestoring redundancy and/or rebalancing data or load.

Each storage node 150 can have multiple components. In the embodimentshown here, the storage node 150 includes a printed circuit board 158populated by a CPU 156, i.e., processor, a memory 154 coupled to the CPU156, and a non-volatile solid state storage 152 coupled to the CPU 156,although other mountings and/or components could be used in furtherembodiments. The memory 154 has instructions which are executed by theCPU 156 and/or data operated on by the CPU 156. As further explainedbelow, the non-volatile solid state storage 152 includes flash or, infurther embodiments, other types of solid-state memory.

Referring to FIG. 1, storage cluster 160 is scalable, meaning thatstorage capacity with non-uniform storage sizes is readily added, asdescribed above. One or more storage nodes 150 can be plugged into orremoved from each chassis and the storage cluster self-configures insome embodiments. Plug-in storage nodes 150, whether installed in achassis as delivered or later added, can have different sizes. Forexample, in one embodiment a storage node 150 can have any multiple of 4TB, e.g., 8 TB, 12 TB, 16 TB, 32 TB, etc. In further embodiments, astorage node 150 could have any multiple of other storage amounts orcapacities. Storage capacity of each storage node 150 is broadcast, andinfluences decisions of how to stripe the data. For maximum storageefficiency, an embodiment can self-configure as wide as possible in thestripe, subject to a predetermined requirement of continued operationwith loss of up to one, or up to two, non-volatile solid state storageunits 152 or storage nodes 150 within the chassis.

FIG. 2 is a block diagram showing a communications interconnect 170 andpower distribution bus 172 coupling multiple storage nodes 150.Referring back to FIG. 1, the communications interconnect 170 can beincluded in or implemented with the switch fabric 146 in someembodiments. Where multiple storage clusters 160 occupy a rack, thecommunications interconnect 170 can be included in or implemented with atop of rack switch, in some embodiments. As illustrated in FIG. 2,storage cluster 160 is enclosed within a single chassis 138. Externalport 176 is coupled to storage nodes 150 through communicationsinterconnect 170, while external port 174 is coupled directly to astorage node. External power port 178 is coupled to power distributionbus 172. Storage nodes 150 may include varying amounts and differingcapacities of non-volatile solid state storage 152 as described withreference to FIG. 1. In addition, one or more storage nodes 150 may be acompute only storage node as illustrated in FIG. 2. Authorities 168 areimplemented on the non-volatile solid state storages 152, for example aslists or other data structures stored in memory. In some embodiments theauthorities are stored within the non-volatile solid state storage 152and supported by software executing on a controller or other processorof the non-volatile solid state storage 152. In a further embodiment,authorities 168 are implemented on the storage nodes 150, for example aslists or other data structures stored in the memory 154 and supported bysoftware executing on the CPU 156 of the storage node 150. Authorities168 control how and where data is stored in the non-volatile solid statestorages 152 in some embodiments. This control assists in determiningwhich type of erasure coding scheme is applied to the data, and whichstorage nodes 150 have which portions of the data. Each authority 168may be assigned to a non-volatile solid state storage 152. Eachauthority may control a range of inode numbers, segment numbers, orother data identifiers which are assigned to data by a file system, bythe storage nodes 150, or by the non-volatile solid state storage 152,in various embodiments.

Every piece of data, and every piece of metadata, has redundancy in thesystem in some embodiments. In addition, every piece of data and everypiece of metadata has an owner, which may be referred to as anauthority. If that authority is unreachable, for example through failureof a storage node, there is a plan of succession for how to find thatdata or that metadata. In various embodiments, there are redundantcopies of authorities 168. Authorities 168 have a relationship tostorage nodes 150 and non-volatile solid state storage 152 in someembodiments. Each authority 168, covering a range of data segmentnumbers or other identifiers of the data, may be assigned to a specificnon-volatile solid state storage 152. In some embodiments theauthorities 168 for all of such ranges are distributed over thenon-volatile solid state storages 152 of a storage cluster. Each storagenode 150 has a network port that provides access to the non-volatilesolid state storage(s) 152 of that storage node 150. Data can be storedin a segment, which is associated with a segment number and that segmentnumber is an indirection for a configuration of a RAID (redundant arrayof independent disks) stripe in some embodiments. The assignment and useof the authorities 168 thus establishes an indirection to data.Indirection may be referred to as the ability to reference dataindirectly, in this case via an authority 168, in accordance with someembodiments. A segment identifies a set of non-volatile solid statestorage 152 and a local identifier into the set of non-volatile solidstate storage 152 that may contain data. In some embodiments, the localidentifier is an offset into the device and may be reused sequentiallyby multiple segments. In other embodiments the local identifier isunique for a specific segment and never reused. The offsets in thenon-volatile solid state storage 152 are applied to locating data forwriting to or reading from the non-volatile solid state storage 152 (inthe form of a RAID stripe). Data is striped across multiple units ofnon-volatile solid state storage 152, which may include or be differentfrom the non-volatile solid state storage 152 having the authority 168for a particular data segment.

If there is a change in where a particular segment of data is located,e.g., during a data move or a data reconstruction, the authority 168 forthat data segment should be consulted, at that non-volatile solid statestorage 152 or storage node 150 having that authority 168. In order tolocate a particular piece of data, embodiments calculate a hash valuefor a data segment or apply an inode number or a data segment number.The output of this operation points to a non-volatile solid statestorage 152 having the authority 168 for that particular piece of data.In some embodiments there are two stages to this operation. The firststage maps an entity identifier (ID), e.g., a segment number, inodenumber, or directory number to an authority identifier. This mapping mayinclude a calculation such as a hash or a bit mask. The second stage ismapping the authority identifier to a particular non-volatile solidstate storage 152, which may be done through an explicit mapping. Theoperation is repeatable, so that when the calculation is performed, theresult of the calculation repeatably and reliably points to a particularnon-volatile solid state storage 152 having that authority 168. Theoperation may include the set of reachable storage nodes as input. Ifthe set of reachable non-volatile solid state storage units changes theoptimal set changes. In some embodiments, the persisted value is thecurrent assignment (which is always true) and the calculated value isthe target assignment the cluster will attempt to reconfigure towards.This calculation may be used to determine the optimal non-volatile solidstate storage 152 for an authority in the presence of a set ofnon-volatile solid state storage 152 that are reachable and constitutethe same cluster. The calculation also determines an ordered set of peernon-volatile solid state storage 152 that will also record the authorityto non-volatile solid state storage mapping so that the authority may bedetermined even if the assigned non-volatile solid state storage isunreachable. A duplicate or substitute authority 168 may be consulted ifa specific authority 168 is unavailable in some embodiments.

With reference to FIGS. 1 and 2, two of the many tasks of the CPU 156 ona storage node 150 are to break up write data, and reassemble read data.When the system has determined that data is to be written, the authority168 for that data is located as above. When the segment ID for data isalready determined the request to write is forwarded to the non-volatilesolid state storage 152 currently determined to be the host of theauthority 168 determined from the segment. The host CPU 156 of thestorage node 150, on which the non-volatile solid state storage 152 andcorresponding authority 168 reside, then breaks up or shards the dataand transmits the data out to various non-volatile solid state storage152. The transmitted data is written as a data stripe in accordance withan erasure coding scheme. In some embodiments, data is requested to bepulled, and in other embodiments, data is pushed. In reverse, when datais read, the authority 168 for the segment ID containing the data islocated as described above. The host CPU 156 of the storage node 150 onwhich the non-volatile solid state storage 152 and correspondingauthority 168 reside requests the data from the non-volatile solid statestorage and corresponding storage nodes pointed to by the authority. Insome embodiments the data is read from flash storage as a data stripe.The host CPU 156 of storage node 150 then reassembles the read data,correcting any errors (if present) according to the appropriate erasurecoding scheme, and forwards the reassembled data to the network. Infurther embodiments, some or all of these tasks can be handled in thenon-volatile solid state storage 152. In some embodiments, the segmenthost requests the data be sent to storage node 150 by requesting pagesfrom storage and then sending the data to the storage node making theoriginal request.

In some systems, for example in UNIX-style file systems, data is handledwith an index node or inode, which specifies a data structure thatrepresents an object in a file system. The object could be a file or adirectory, for example. Metadata may accompany the object, as attributessuch as permission data and a creation timestamp, among otherattributes. A segment number could be assigned to all or a portion ofsuch an object in a file system. In other systems, data segments arehandled with a segment number assigned elsewhere. For purposes ofdiscussion, the unit of distribution is an entity, and an entity can bea file, a directory or a segment. That is, entities are units of data ormetadata stored by a storage system. Entities are grouped into setscalled authorities. Each authority has an authority owner, which is astorage node that has the exclusive right to update the entities in theauthority. In other words, a storage node contains the authority, andthat the authority, in turn, contains entities.

A segment is a logical container of data in accordance with someembodiments. A segment is an address space between medium address spaceand physical flash locations, i.e., the data segment number, are in thisaddress space. Segments may also contain meta-data, which enable dataredundancy to be restored (rewritten to different flash locations ordevices) without the involvement of higher level software. In oneembodiment, an internal format of a segment contains client data andmedium mappings to determine the position of that data. Each datasegment is protected, e.g., from memory and other failures, by breakingthe segment into a number of data and parity shards, where applicable.The data and parity shards are distributed, i.e., striped, acrossnon-volatile solid state storage 152 coupled to the host CPUs 156 (SeeFIG. 5) in accordance with an erasure coding scheme. Usage of the termsegments refers to the container and its place in the address space ofsegments in some embodiments. Usage of the term stripe refers to thesame set of shards as a segment and includes how the shards aredistributed along with redundancy or parity information in accordancewith some embodiments.

A series of address-space transformations takes place across an entirestorage system. At the top are the directory entries (file names) whichlink to an inode. Modes point into medium address space, where data islogically stored. Medium addresses may be mapped through a series ofindirect mediums to spread the load of large files, or implement dataservices like deduplication or snapshots. Medium addresses may be mappedthrough a series of indirect mediums to spread the load of large files,or implement data services like deduplication or snapshots. Segmentaddresses are then translated into physical flash locations. Physicalflash locations have an address range bounded by the amount of flash inthe system in accordance with some embodiments. Medium addresses andsegment addresses are logical containers, and in some embodiments use a128 bit or larger identifier so as to be practically infinite, with alikelihood of reuse calculated as longer than the expected life of thesystem. Addresses from logical containers are allocated in ahierarchical fashion in some embodiments. Initially, each non-volatilesolid state storage 152 may be assigned a range of address space. Withinthis assigned range, the non-volatile solid state storage 152 is able toallocate addresses without synchronization with other non-volatile solidstate storage 152.

Data and metadata is stored by a set of underlying storage layouts thatare optimized for varying workload patterns and storage devices. Theselayouts incorporate multiple redundancy schemes, compression formats andindex algorithms. Some of these layouts store information aboutauthorities and authority masters, while others store file metadata andfile data. The redundancy schemes include error correction codes thattolerate corrupted bits within a single storage device (such as a NANDflash chip), erasure codes that tolerate the failure of multiple storagenodes, and replication schemes that tolerate data center or regionalfailures. In some embodiments, low density parity check (LDPC) code isused within a single storage unit. Reed-Solomon encoding is used withina storage cluster, and mirroring is used within a storage grid in someembodiments. Metadata may be stored using an ordered log structuredindex (such as a Log Structured Merge Tree), and large data may not bestored in a log structured layout.

In order to maintain consistency across multiple copies of an entity,the storage nodes agree implicitly on two things through calculations:(1) the authority that contains the entity, and (2) the storage nodethat contains the authority. The assignment of entities to authoritiescan be done by pseudorandomly assigning entities to authorities, bysplitting entities into ranges based upon an externally produced key, orby placing a single entity into each authority. Examples of pseudorandomschemes are linear hashing and the Replication Under Scalable Hashing(RUSH) family of hashes, including Controlled Replication Under ScalableHashing (CRUSH). In some embodiments, pseudo-random assignment isutilized only for assigning authorities to nodes because the set ofnodes can change. The set of authorities cannot change so any subjectivefunction may be applied in these embodiments. Some placement schemesautomatically place authorities on storage nodes, while other placementschemes rely on an explicit mapping of authorities to storage nodes. Insome embodiments, a pseudorandom scheme is utilized to map from eachauthority to a set of candidate authority owners. A pseudorandom datadistribution function related to CRUSH may assign authorities to storagenodes and create a list of where the authorities are assigned. Eachstorage node has a copy of the pseudorandom data distribution function,and can arrive at the same calculation for distributing, and laterfinding or locating an authority. Each of the pseudorandom schemesrequires the reachable set of storage nodes as input in some embodimentsin order to conclude the same target nodes. Once an entity has beenplaced in an authority, the entity may be stored on physical devices sothat no expected failure will lead to unexpected data loss. In someembodiments, rebalancing algorithms attempt to store the copies of allentities within an authority in the same layout and on the same set ofmachines.

Examples of expected failures include device failures, stolen machines,datacenter fires, and regional disasters, such as nuclear or geologicalevents. Different failures lead to different levels of acceptable dataloss. In some embodiments, a stolen storage node impacts neither thesecurity nor the reliability of the system, while depending on systemconfiguration, a regional event could lead to no loss of data, a fewseconds or minutes of lost updates, or even complete data loss.

In the embodiments, the placement of data for storage redundancy isindependent of the placement of authorities for data consistency. Insome embodiments, storage nodes that contain authorities do not containany persistent storage. Instead, the storage nodes are connected tonon-volatile solid state storage units that do not contain authorities.The communications interconnect between storage nodes and non-volatilesolid state storage units consists of multiple communicationtechnologies and has non-uniform performance and fault tolerancecharacteristics. In some embodiments, as mentioned above, non-volatilesolid state storage units are connected to storage nodes via PCIexpress, storage nodes are connected together within a single chassisusing Ethernet backplane, and chassis are connected together to form astorage cluster. Storage clusters are connected to clients usingEthernet or fiber channel in some embodiments. If multiple storageclusters are configured into a storage grid, the multiple storageclusters are connected using the Internet or other long-distancenetworking links, such as a “metro scale” link or private link that doesnot traverse the internet.

Authority owners have the exclusive right to modify entities, to migrateentities from one non-volatile solid state storage unit to anothernon-volatile solid state storage unit, and to add and remove copies ofentities. This allows for maintaining the redundancy of the underlyingdata. When an authority owner fails, is going to be decommissioned, oris overloaded, the authority is transferred to a new storage node.Transient failures make it non-trivial to ensure that all non-faultymachines agree upon the new authority location. The ambiguity thatarises due to transient failures can be achieved automatically by aconsensus protocol such as Paxos, hot-warm failover schemes, via manualintervention by a remote system administrator, or by a local hardwareadministrator (such as by physically removing the failed machine fromthe cluster, or pressing a button on the failed machine). In someembodiments, a consensus protocol is used, and failover is automatic. Iftoo many failures or replication events occur in too short a timeperiod, the system goes into a self-preservation mode and haltsreplication and data movement activities until an administratorintervenes in accordance with some embodiments.

As authorities are transferred between storage nodes and authorityowners update entities in their authorities, the system transfersmessages between the storage nodes and non-volatile solid state storageunits. With regard to persistent messages, messages that have differentpurposes are of different types. Depending on the type of the message,the system maintains different ordering and durability guarantees. Asthe persistent messages are being processed, the messages aretemporarily stored in multiple durable and non-durable storage hardwaretechnologies. In some embodiments, messages are stored in RAM, NVRAM andon NAND flash devices, and a variety of protocols are used in order tomake efficient use of each storage medium. Latency-sensitive clientrequests may be persisted in replicated NVRAM, and then later NAND,while background rebalancing operations are persisted directly to NAND.

Persistent messages are persistently stored prior to being replicated.This allows the system to continue to serve client requests despitefailures and component replacement. Although many hardware componentscontain unique identifiers that are visible to system administrators,manufacturer, hardware supply chain and ongoing monitoring qualitycontrol infrastructure, applications running on top of theinfrastructure address virtualize addresses. These virtualized addressesdo not change over the lifetime of the storage system, regardless ofcomponent failures and replacements. This allows each component of thestorage system to be replaced over time without reconfiguration ordisruptions of client request processing.

In some embodiments, the virtualized addresses are stored withsufficient redundancy. A continuous monitoring system correlateshardware and software status and the hardware identifiers. This allowsdetection and prediction of failures due to faulty components andmanufacturing details. The monitoring system also enables the proactivetransfer of authorities and entities away from impacted devices beforefailure occurs by removing the component from the critical path in someembodiments.

FIG. 3 is a multiple level block diagram, showing contents of a storagenode 150 and contents of a non-volatile solid state storage 152 of thestorage node 150. Data is communicated to and from the storage node 150by a network interface controller (NIC) 202 in some embodiments. Eachstorage node 150 has a CPU 156, and one or more non-volatile solid statestorage 152, as discussed above. Moving down one level in FIG. 3, eachnon-volatile solid state storage 152 has a relatively fast non-volatilesolid state memory, such as nonvolatile random access memory (NVRAM)204, and flash memory 206. In some embodiments, NVRAM 204 may be acomponent that does not require program/erase cycles (DRAM, MRAM, PCM),and can be a memory that can support being written vastly more oftenthan the memory is read from. Moving down another level in FIG. 3, theNVRAM 204 is implemented in one embodiment as high speed volatilememory, such as dynamic random access memory (DRAM) 216, backed up byenergy reserve 218. Energy reserve 218 provides sufficient electricalpower to keep the DRAM 216 powered long enough for contents to betransferred to the flash memory 206 in the event of power failure. Insome embodiments, energy reserve 218 is a capacitor, super-capacitor,battery, or other device, that supplies a suitable supply of energysufficient to enable the transfer of the contents of DRAM 216 to astable storage medium in the case of power loss. The flash memory 206 isimplemented as multiple flash dies 222, which may be referred to aspackages of flash dies 222 or an array of flash dies 222. It should beappreciated that the flash dies 222 could be packaged in any number ofways, with a single die per package, multiple dies per package (i.e.multichip packages), in hybrid packages, as bare dies on a printedcircuit board or other substrate, as encapsulated dies, etc. In theembodiment shown, the non-volatile solid state storage 152 has acontroller 212 or other processor, and an input output (I/O) port 210coupled to the controller 212. I/O port 210 is coupled to the CPU 156and/or the network interface controller 202 of the flash storage node150. Flash input output (I/O) port 220 is coupled to the flash dies 222,and a direct memory access unit (DMA) 214 is coupled to the controller212, the DRAM 216 and the flash dies 222. In the embodiment shown, theI/O port 210, controller 212, DMA unit 214 and flash I/O port 220 areimplemented on a programmable logic device (PLD) 208, e.g., a fieldprogrammable gate array (FPGA). In this embodiment, each flash die 222has pages, organized as sixteen kB (kilobyte) pages 224, and a register226 through which data can be written to or read from the flash die 222.In further embodiments, other types of solid-state memory are used inplace of, or in addition to flash memory illustrated within flash die222.

Storage cluster 160, in various embodiments as disclosed herein, can becontrasted with storage arrays in general. The storage nodes 150 arepart of a collection that creates the storage cluster 160. Each storagenode 150 owns a slice of data and computing required to provide thedata. Multiple storage nodes 150 cooperate to store and retrieve thedata. Storage memory or storage devices, as used in storage arrays ingeneral, are less involved with processing and manipulating the data.Storage memory or storage devices in a storage array receive commands toread, write, or erase data. The storage memory or storage devices in astorage array are not aware of a larger system in which they areembedded, or what the data means. Storage memory or storage devices instorage arrays can include various types of storage memory, such as RAM,solid state drives, hard disk drives, etc. The storage units 152described herein have multiple interfaces active simultaneously andserving multiple purposes. In some embodiments, some of thefunctionality of a storage node 150 is shifted into a storage unit 152,transforming the storage unit 152 into a combination of storage unit 152and storage node 150. Placing computing (relative to storage data) intothe storage unit 152 places this computing closer to the data itself.The various system embodiments have a hierarchy of storage node layerswith different capabilities. By contrast, in a storage array, acontroller owns and knows everything about all of the data that thecontroller manages in a shelf or storage devices. In a storage cluster160, as described herein, multiple controllers in multiple storage units152 and/or storage nodes 150 cooperate in various ways (e.g., forerasure coding, data sharding, metadata communication and redundancy,storage capacity expansion or contraction, data recovery, and so on).

FIG. 4 is a front view of a storage cluster 160, in a single chassis138, partitioned into multiple logical arrays 404, 406 or clusters. Eachlogical array 404 functions as a storage cluster, with a unique clusteridentifier in some embodiments. The chassis 138 houses the storage nodes150 of the storage cluster 160, and also houses a switch fabric 146 orother bus or network that couples the storage nodes 150 as the storagecluster. A power supply 402 occupies part of the chassis 138, or couldbe external to the chassis 138 in various embodiments. As shown in FIG.4, the storage cluster 160, which may be considered a physical array, ispartitioned into two logical arrays 404, 406. In various embodiments,the storage cluster 160 could be partitioned into further logicalarrays. A visual indicator 412 on each storage node 150, in someembodiments, shows a number, letter, symbol, color or other visualindication corresponding to the assignment of the storage node 150relative to one or more logical arrays 404, 406. That is, the visualindicator 412 shows the membership of a particular storage node 150 to aparticular logical array 404, or other membership or assignment statusof the storage node 150. For example, the visual indicator 412 couldshow the letter “A”, the number “1”, or other name or label for astorage node 150 assigned to a particular logical array 404. In someembodiments, the visual indicator 412 can indicate when a storage node150 is unassigned, for example when the storage node 150 is anunassigned spare. In further embodiments, the visual indicator 412 canindicate when a storage node 150 is shared by multiple logical arrays404, 406. Since each storage unit 152 and each storage node 150 has aprocessor and local memory, the storage units 152 and storage nodes 150of the storage cluster 160 can be programmed for various features aswill be further described below. It should be appreciated that variousembodiments can have one or a small number of these features, or alarger number of features, in various combinations.

FIG. 5 is a front view of a storage cluster 160 spanning two chassis138, partitioned into multiple logical arrays 404, 406, 408, 410 orclusters. As in FIG. 4, storage nodes 150 in one chassis 138 can beassigned to a particular logical array 404, 406. In the embodimentshown, a logical array 408 can span more than one chassis 138. That is,storage nodes 150 in two or more chassis 138 can be assigned to aparticular logical array 408. To facilitate communication among suchstorage nodes 150 in a logical array 408 spanning two or more chassis138, these chassis 138 are coupled together, for example by a bus or anetwork that couples the storage nodes 150 of the two or more chassis138 together.

With reference to FIGS. 4 and 5, various features and combinations ofthese features are possible with the embodiments described herein. Insome embodiments, the assignment of a storage node 150 to a logicalarray 404 depends on the slot 142 of the chassis 138 (see FIG. 1). Inother embodiments, the assignment of a storage node 150 to a logicalarray 404, 406, 408, 410 is slot independent. It is not necessary tohave all slots 142 in a chassis 138 occupied by storage nodes 150, sincea storage node 150 can be hot plugged into a slot 142, and assigned to alogical array 404, 406, 408, 410. Alternatively, a storage node 150could occupy a slot but be unassigned, and then assigned to one of thelogical arrays 404, 406, 408, 410. Various degrees and types of sharedand separate facilities are also possible. For example, the storagecluster 160 could have a shared physical network, and also have networkseparation using virtual local area networks, one for each logical array404, 406, 408, 410. Each logical array 404, 406 could have a uniqueInternet protocol address, a unique virtual local area network name,unique software image and version, etc. Flow-based control could beapplied to reconfigure one or more of these virtual local area networksor route communication over different paths in the virtual local areanetworks. Software separation allows for independent software,independent operating systems, independent upgrades of software,independent upgrades of operating systems and so on. For example, eachlogical array 404, 406 could have its own operating system, software,software upgrades, operating system upgrades, hardware upgrades, etc.

Management isolation allows for separate ports and separate managementof each logical array 404, 406. For example, each logical array 404could be accessed and managed via a port belonging to one of the storagenodes 150 assigned to that logical array 404, or a port belonging to avirtual local area network assigned to that logical array 404. Thenumber of storage nodes 150 assigned to one logical array 404 isindependent of the number of storage nodes 150 assigned to anotherlogical array 406. Total storage capacity, or utilized or spare storagecapacity, of one logical array 404 is independent of that of anotherlogical array 406. Redundancy schemes and/or encryption schemes candiffer from one logical array 404 to another logical array 406. Logicalarrays 404, 406, 408, 410 can have administrative domain isolation.

In some embodiments, there could be shared data and/or shared datastriping across storage nodes 150 of multiple logical arrays 404, 406,and separate metadata and control for each logical array 404, 406. Inother embodiments, there could be shared data and/or shared datastriping, and shared metadata and control across storage nodes 150 ofmultiple logical arrays 404, 406. There could be shared data and/orshared data striping, and shared metadata across storage nodes 150 ofmultiple logical arrays 404, 406, and separate control and processingfor each logical array 404, 406. In embodiments with shared datastriping, there could be wider stripes (e.g., across most or all of thestorage nodes 150 of a storage cluster 160) than would be possible forembodiments with the same total number of storage nodes 150 but datastriping limited to the storage nodes 150 assigned to a particularlogical array 404, 406. Data striping could even extend across storagenodes 150 of two or more chassis 138.

Some embodiments have a high degree of isolation, with data, datastriping, metadata, control, processing, and communication of onelogical array 404 isolated and independent of that of another logicalarray 406. With this degree of isolation, there is no communication frommembers of one storage cluster (e.g., storage nodes 150 assigned to onelogical array 404) to members of another storage cluster (e.g., storagenodes 150 assigned to another logical array 406), and vice versa. Nodata from one logical array 404, and no metadata from one logical array404, is found in storage nodes 150 assigned to another logical array406, and vice versa. This high degree of isolation allows for corruptionisolation, for example arising from faults in processing. That is, acorruption in one logical array 404 or cluster does not affect anotherlogical array 406 or cluster.

Some embodiments can dynamically shift compute resources from onelogical array 404 to another logical array 406. In some versions, thestorage cluster 160 has one or more compute nodes, such as shown in FIG.2 as a “storage nodes compute only” storage node 150. Logical arrays404, 406 could be provisioned with one or more compute nodes each insome embodiments. The compute node or nodes communicate with otherstorage nodes 150 of the logical array 404. With one or more computenodes, a logical array 404, 406, 408, 410 can function as both a storagearray and a computing facility, and execute applications as well asstore user data, for example. In versions supporting multiple chassis138, one or more compute nodes from one chassis 138 could be assigned tological arrays 404, 406, 408, 410 with storage nodes 150 of either orany of the multiple chassis 138. This is regardless of the slot 142 (seeFIG. 1) any storage node occupies.

Some embodiments have ability to remove a storage node 150 from alogical array 404. This can happen in various ways. If a storage node150 fails, the system can recover user data, using erasure coding,reconfigure, and redistribute user data among remaining storage nodes150, using the same or a differing version of erasure coding. Physicallyremoving a storage node 150 from a chassis 138 could trigger suchactions, as if the storage node 150 had failed. In this case, theremoved storage node 150 still contains portions of user data andmetadata, which can be recovered upon reinsertion of the storage node150 into the same chassis 138, or a differing chassis 138 in someembodiments. However, in some embodiments, a command to evacuate astorage node 150 of data and metadata causes the corresponding logicalarray 404 (of which that storage node 150 is a member) to do so and toredistribute the data and the metadata throughout the remaining storagenodes 150 of that logical array 404. The evacuated storage node 150 canthen be physically removed from the chassis 138 as empty, left in thechassis 138 as unassigned (e.g., a spare, or reserve capacity), orassigned to another logical array 406. In some versions, one or more ofthe storage nodes 150 has the capability of being evacuated and removedor reassigned, and one or more of the storage nodes 150 lacks thiscapability and should not be removed from a logical array 404 onceassigned to that logical array 404. The visual indicator 412 could showa symbol, color or message, etc., to indicate that this storage node 150is prevented from being removed. Similarly, the visual indicator 412could show a storage node 150 is removable, if such is the case. Arequest to remove a storage node 150 could be followed by adetermination of whether that storage node 150 is of a type that isremovable, or a type that is not removable, which could then becommunicated by message or report.

Some embodiments have automatic provisioning of a logical array 404.Other embodiments have manual provisioning of each logical array 404. Astorage cluster 160 could be setup for manual provisioning of one ormore logical arrays 404, and automatic provision of one or more logicalarrays 406. A licensing model can be implemented in some embodiments ofthe storage cluster 160. A manufacturer would supply one or more chassis138 populated by storage nodes 150, but not all of the storage nodes 150would be assigned to a particular logical array 404 (or multiple logicalarrays 404, 406). The storage cluster 160 would self-monitor, andcommunicate back to the manufacturer regarding utilized storagecapacity. When the storage cluster 160 assigns an unassigned storagenode 150 to a logical array 404, whether automatically or by clientinstruction, the storage cluster 160 communicates this event andsituation (e.g., in a report or message) back to the manufacturer. Themanufacturer can then bill or debit the user for the additional storagecapacity at the time this additional capacity is brought online. Thismay be referred to as a “purchase on first use model”. In some versions,the storage cluster 160 communicates when a storage node 150 is removedfrom a logical array 404 and associated storage cluster. Themanufacturer could then refund or credit a user, or discontinue billingfor any removed storage node 150, in a flexible billing plan based onstorage usage. In some embodiments, a storage node 150 can be assignedto be removable or non-removable. Non-removable storage nodes 150 wouldremain as assigned to a logical array 404, and could not be removed, norwould a refund or credit be issued if storage capacity of such anon-removable storage node 150 is not used, in the flexible billingplan.

FIG. 6 is a flow diagram of a method for partitioning a storage clusterinto multiple logical arrays and performing data striping of user datain accordance with the multiple logical arrays, which can be practicedon embodiments of the storage cluster, storage nodes and storage unitsof FIGS. 1-5. The method can be practiced by processors of storage nodesand/or storage units. In an action 602, a first set of storage nodes isassigned to a first logical array. Metadata, control, and data stripingscheme for user data belonging to the first logical array areestablished, in an action 604. In various embodiments, there are variouscapabilities for each of these to be isolated to storage nodes of thefirst logical array, or shared across storage nodes of the storagecluster (i.e., shared across storage nodes assigned to multiple logicalarrays) in various combinations. For example, authorities and wards(i.e., owners of user data) could be established in storage nodesassigned to the first logical array, with metadata, control and datastriping confined to nodes assigned to the first logical array, ormetadata, control and/or data striping shared across nodes of the firstlogical array and another logical array, etc.

In an action 606, a second set of storage nodes is assigned to a secondlogical array. Metadata, control, and data striping scheme for user databelonging to the second logical array are established, in an action 608.The second logical array, and storage nodes assigned to the secondlogical array has similar capabilities and possibilities in variousembodiments as the first logical array and corresponding storage nodes.Assignment status of each storage node is indicated, in an action 610.For example, the visual indicator described above with reference to FIG.4 shows a visual indication of whether a storage node is assigned to aparticular logical array, or is shared or unassigned. Data striping foruser data belonging to the first logical array is performed in an action612. This is according to the data striping scheme established in theaction 604, which could be for data striping across storage nodesassigned to the first logical array, or for data striping across storagenodes assigned to the first logical array and the second logical array,etc. Data striping for user data belonging to the second logical arrayis performed in an action 614. This is according to the data stripingscheme established in the action 608, which could be for data stripingacross storage nodes assigned to the second logical array, or for datastriping across storage nodes assigned to the first logical array andthe second logical array, etc.

In a decision action 616, it is determined whether to shift computeresources. This could be based on a request, e.g., from a client, orautomatic load balancing of compute resources, etc. If the answer is no,flow proceeds to the decision action 620. If the answer is yes, computeresources should be shifted, flow proceeds to the action 618, where acompute node is reassigned from one logical array to another logicalarray. Flow then proceeds to the decision action 620 where it isdetermined whether to shift storage resources. This determination couldbe based on a request, e.g., from a client, or automatic load balancingof storage resources, etc. If the answer is no, flow branches back tothe action 612, to continue performing data striping. Alternatively,flow could branch elsewhere to perform further actions ordeterminations. If the answer is yes, flow proceeds to the action 622,where a storage node is reassigned from one logical array to anotherlogical array. The reassignment could include evacuating data andmetadata from the storage node, removing the storage node from onelogical array, declaring that the storage node is unassigned, and thenassigning the storage node to the other logical array, as describedabove with reference to FIGS. 4 and 5. After reassigning the storagenode, the flow proceeds back to the action 612, to continue datastriping. Alternatively, flow could proceed elsewhere to perform furtheractions or determinations.

It should be appreciated that the methods described herein may beperformed with a digital processing system, such as a conventional,general-purpose computer system. Special purpose computers, which aredesigned or programmed to perform only one function may be used in thealternative. FIG. 7 is an illustration showing an exemplary computingdevice which may implement the embodiments described herein. Thecomputing device of FIG. 7 may be used to perform embodiments of thefunctionality for a storage node or a non-volatile solid state storagein accordance with some embodiments. The computing device includes acentral processing unit (CPU) 701, which is coupled through a bus 705 toa memory 703, and mass storage device 707. Mass storage device 707represents a persistent data storage device such as a disc drive, whichmay be local or remote in some embodiments. The mass storage device 707could implement a backup storage, in some embodiments. Memory 703 mayinclude read only memory, random access memory, etc. Applicationsresident on the computing device may be stored on or accessed via acomputer readable medium such as memory 703 or mass storage device 707in some embodiments. Applications may also be in the form of modulatedelectronic signals modulated accessed via a network modem or othernetwork interface of the computing device. It should be appreciated thatCPU 701 may be embodied in a general-purpose processor, a specialpurpose processor, or a specially programmed logic device in someembodiments.

Display 711 is in communication with CPU 701, memory 703, and massstorage device 707, through bus 705. Display 711 is configured todisplay any visualization tools or reports associated with the systemdescribed herein. Input/output device 709 is coupled to bus 705 in orderto communicate information in command selections to CPU 701. It shouldbe appreciated that data to and from external devices may becommunicated through the input/output device 709. CPU 701 can be definedto execute the functionality described herein to enable thefunctionality described with reference to FIGS. 1-6. The code embodyingthis functionality may be stored within memory 703 or mass storagedevice 707 for execution by a processor such as CPU 701 in someembodiments. The operating system on the computing device may beMS-WINDOWS™, UNIX™, LINUX™, iOS™, CentOS™, Android™, Redhat Linux™,z/OS™, or other known operating systems. It should be appreciated thatthe embodiments described herein may be integrated with virtualizedcomputing system also.

Detailed illustrative embodiments are disclosed herein. However,specific functional details disclosed herein are merely representativefor purposes of describing embodiments. Embodiments may, however, beembodied in many alternate forms and should not be construed as limitedto only the embodiments set forth herein.

It should be understood that although the terms first, second, etc. maybe used herein to describe various steps or calculations, these steps orcalculations should not be limited by these terms. These terms are onlyused to distinguish one step or calculation from another. For example, afirst calculation could be termed a second calculation, and, similarly,a second step could be termed a first step, without departing from thescope of this disclosure. As used herein, the term “and/or” and the “/”symbol includes any and all combinations of one or more of theassociated listed items.

As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”,“comprising”, “includes”, and/or “including”, when used herein, specifythe presence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof. Therefore, the terminology usedherein is for the purpose of describing particular embodiments only andis not intended to be limiting.

It should also be noted that in some alternative implementations, thefunctions/acts noted may occur out of the order noted in the figures.For example, two figures shown in succession may in fact be executedsubstantially concurrently or may sometimes be executed in the reverseorder, depending upon the functionality/acts involved.

With the above embodiments in mind, it should be understood that theembodiments might employ various computer-implemented operationsinvolving data stored in computer systems. These operations are thoserequiring physical manipulation of physical quantities. Usually, thoughnot necessarily, these quantities take the form of electrical ormagnetic signals capable of being stored, transferred, combined,compared, and otherwise manipulated. Further, the manipulationsperformed are often referred to in terms, such as producing,identifying, determining, or comparing. Any of the operations describedherein that form part of the embodiments are useful machine operations.The embodiments also relate to a device or an apparatus for performingthese operations. The apparatus can be specially constructed for therequired purpose, or the apparatus can be a general-purpose computerselectively activated or configured by a computer program stored in thecomputer. In particular, various general-purpose machines can be usedwith computer programs written in accordance with the teachings herein,or it may be more convenient to construct a more specialized apparatusto perform the required operations.

A module, an application, a layer, an agent or other method-operableentity could be implemented as hardware, firmware, or a processorexecuting software, or combinations thereof. It should be appreciatedthat, where a software-based embodiment is disclosed herein, thesoftware can be embodied in a physical machine such as a controller. Forexample, a controller could include a first module and a second module.A controller could be configured to perform various actions, e.g., of amethod, an application, a layer or an agent.

The embodiments can also be embodied as computer readable code on anon-transitory computer readable medium. The computer readable medium isany data storage device that can store data, which can be thereafterread by a computer system. Examples of the computer readable mediuminclude hard drives, network attached storage (NAS), read-only memory,random-access memory, CD-ROMs, CD-Rs, CD-RWs, magnetic tapes, and otheroptical and non-optical data storage devices. The computer readablemedium can also be distributed over a network coupled computer system sothat the computer readable code is stored and executed in a distributedfashion. Embodiments described herein may be practiced with variouscomputer system configurations including hand-held devices, tablets,microprocessor systems, microprocessor-based or programmable consumerelectronics, minicomputers, mainframe computers and the like. Theembodiments can also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a wire-based or wireless network.

Although the method operations were described in a specific order, itshould be understood that other operations may be performed in betweendescribed operations, described operations may be adjusted so that theyoccur at slightly different times or the described operations may bedistributed in a system which allows the occurrence of the processingoperations at various intervals associated with the processing.

In various embodiments, one or more portions of the methods andmechanisms described herein may form part of a cloud-computingenvironment. In such embodiments, resources may be provided over theInternet as services according to one or more various models. Suchmodels may include Infrastructure as a Service (IaaS), Platform as aService (PaaS), and Software as a Service (SaaS). In IaaS, computerinfrastructure is delivered as a service. In such a case, the computingequipment is generally owned and operated by the service provider. Inthe PaaS model, software tools and underlying equipment used bydevelopers to develop software solutions may be provided as a serviceand hosted by the service provider. SaaS typically includes a serviceprovider licensing software as a service on demand. The service providermay host the software, or may deploy the software to a customer for agiven period of time. Numerous combinations of the above models arepossible and are contemplated.

Various units, circuits, or other components may be described or claimedas “configured to” perform a task or tasks. In such contexts, the phrase“configured to” is used to connote structure by indicating that theunits/circuits/components include structure (e.g., circuitry) thatperforms the task or tasks during operation. As such, theunit/circuit/component can be said to be configured to perform the taskeven when the specified unit/circuit/component is not currentlyoperational (e.g., is not on). The units/circuits/components used withthe “configured to” language include hardware—for example, circuits,memory storing program instructions executable to implement theoperation, etc. Reciting that a unit/circuit/component is “configuredto” perform one or more tasks is expressly intended not to invoke 35U.S.C. 112, sixth paragraph, for that unit/circuit/component.Additionally, “configured to” can include generic structure (e.g.,generic circuitry) that is manipulated by software and/or firmware(e.g., an FPGA or a general-purpose processor executing software) tooperate in manner that is capable of performing the task(s) at issue.“Configured to” may also include adapting a manufacturing process (e.g.,a semiconductor fabrication facility) to fabricate devices (e.g.,integrated circuits) that are adapted to implement or perform one ormore tasks.

The foregoing description, for the purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the embodiments and its practical applications, to therebyenable others skilled in the art to best utilize the embodiments andvarious modifications as may be suited to the particular usecontemplated. Accordingly, the present embodiments are to be consideredas illustrative and not restrictive, and the invention is not to belimited to the details given herein, but may be modified within thescope and equivalents of the appended claims.

What is claimed is:
 1. A storage system comprising: a plurality ofstorage nodes comprising storage memory; and a plurality of authoritiesassociated with the storage nodes, the plurality of authoritiescontrolling data and metadata of two or more logical storage arrays as aconfiguration of the plurality of storage nodes, wherein at least one ofthe plurality of storage nodes include differing types of solid statememory.
 2. The storage system of claim 1, wherein the plurality ofstorage nodes comprises one or more compute nodes that are assignable toa logical storage array and re-assignable to another logical storagearray.
 3. The storage system of claim 1, wherein the plurality ofstorage nodes comprises a plurality of storage-only nodes or storage andcompute nodes that are each assignable to a logical storage array andre-assignable to another logical storage array.
 4. The storage system ofclaim 1, wherein the plurality of authorities are configurable for datastriping across storage nodes assigned to a first logical storage arrayand data striping across storage nodes assigned to a second logicalstorage array, and configurable for data striping across storage nodesassigned to both the first logical storage array and the second logicalstorage array.
 5. The storage system of claim 1, wherein a first set ofauthorities and associated metadata, control and data striping of afirst logical storage array are isolated from a second set ofauthorities and associated metadata, control and data striping of asecond logical storage array.
 6. The storage system of claim 1, whereinat least a subset of the plurality of authorities and associatedmetadata, control and data striping are shared across a first logicalstorage array and a second logical storage array.
 7. The storage systemof claim 1, further comprising: each of the two or more logical storagearrays configurable to function as both a storage array and a computingfacility to execute one or more applications.
 8. A storage system,comprising: a plurality of storage nodes comprising storage memory and aplurality of authorities greater in number than the plurality of storagenodes; and the plurality of storage nodes to: configure the plurality ofstorage nodes as two or more logical storage arrays; and control, by theplurality of authorities, data and metadata of the two or more logicalstorage arrays, wherein at least one of the plurality of storage nodesinclude differing types of solid state memory.
 9. The storage system ofclaim 8, wherein the plurality of storage nodes are further to: assigneach of one or more of the plurality of storage nodes as a compute nodeto a logical storage array; and reassign each of the one or more of theplurality of storage nodes, as the compute node, to another logicalstorage array.
 10. The storage system of claim 8, wherein the pluralityof storage nodes are further to: assign each of one or more of theplurality of storage nodes as a storage-only node or storage and computenode to a logical storage array; and reassign each of the one or more ofthe plurality of storage nodes as the storage-only node or storage andcompute node to another logical storage array.
 11. The storage system ofclaim 8, wherein the processors of the plurality of storage nodes arefurther to: isolate a first set of authorities and associated metadata,control and striping of a first logical storage array from a second setof authorities and associated metadata, control and data striping of asecond logical storage array.
 12. The storage system of claim 8, whereinthe processors of the plurality of storage nodes are further to: shareat least a subset of the plurality of authorities and associatedmetadata, control and data striping across a first logical storage arrayand a second logical storage array.
 13. The storage system of claim 8,wherein the plurality of storage nodes are further to: execute one ormore applications in one of the logical storage arrays to function asboth a storage array and a computing facility.
 14. A method, comprising:configuring a plurality of storage nodes, comprising storage memory, astwo or more logical storage arrays; and controlling, by a plurality ofauthorities associated with the storage nodes, data and metadata of thetwo or more logical storage arrays, wherein at least one of theplurality of storage nodes include differing types of solid statememory.
 15. The method of claim 14, further comprising: assigning one ormore of the plurality of storage nodes each as a compute node to one ofthe two or more logical storage arrays; and reassigning the one or moreof the plurality of storage nodes each as the compute node to anotherone of the two or more logical storage arrays.
 16. The method of claim14, further comprising: assigning one or more of the plurality ofstorage nodes each as a storage-only node or storage and compute node toone of the two or more logical storage arrays; and reassigning the oneor more of the plurality of storage nodes each as the storage-only nodeor storage and compute node to another one of the two or more logicalstorage arrays.
 17. The method of claim 14, further comprising:isolating a first set of authorities and associated metadata, controland striping of a first one of the two or more logical storage arraysfrom a second set of authorities and associated metadata, control anddata striping of a second one of the two or more logical storage arrays.18. The method of claim 14, further comprising: sharing at least asubset of the plurality of authorities and associated metadata, controland data striping across a first one of the two or more logical storagearrays and a second one of the two or more logical storage arrays. 19.The method of claim 14, further comprising: executing one or moreapplications in each of one or more of the two or more logical storagearrays to function as both a storage array and a computing facility. 20.The method of claim 14, further comprising: displaying, on a visualindicator of the storage system, assignment status of one of theplurality of storage nodes storage node to one of the two or morelogical storage arrays.